The hex values to open Imagine on a larger screen is:
Hex position 0000BEFA and 0000BEFB these two positions contain
the Hex values of 00 and C8. 00C8 in dec is 200. Imagine
auto doubles this value if you've checked interlace in your
prefs. To get the full 482 height, just set the 00C8 to
00F0. 00f0 in dec is 241.
Hex position 0003E348 and 0003E349 these two positions contain
the Hex values of 02 and 80. 0280 in dec is 640. Change
the 0280 to 02E0. 02E0 in bin is 736.
you can try to plug in your own values to adjust the size of Imagine
for the optimum usage of your monitor. DO REMEMBER!!! Make sure that
you have a backup copy before you attempt to `hack' Imagine. The Hex
positions are for the FP version of Imagine 2.x. For editing Imagine,
I use HEX. HEX is a shareware program by Nicola Salmoria. Another editor
that I have used in the past is DEKSID. (disked spelled backwards) DESKID
is also shareware writen by Christian Warren. DEKSID is a bit diffrent
in that it does not display the hex position info. If you use DEKSID,
the positions 0000BEFA and 0000BEFB are in block 95 in positions 0FA and
0FB and positions 0003E348 and 0003E349 are in block 497 positions 148
and 149. And finaly, If you've PowerPacked or Imploded ImagineFP, do
uncrunch it! It's an awfully hard time finding the compressed version
of 0000BEFA!!!! :^) I've noticed that Imagine tends to crash a lot more
often with these changes. It's partly my 040's fault (NEVER BUY AN GVP
GFORCE 040 FOR THE 3000!!!! IT'S ABOUT THE WORST PRODUCT I'VE EVER HAD TO
DEAL WITH!!!!) I might try changing the stack and see if it helps much,
I dought it...
-Ray Collett
collett@agora.rain.com
##
Subject: Re: YET another query...
Date: Wed, 27 Oct 93 10:16:21 MDT
From: pringleg@cuugnet.cuug.ab.ca (Greg Pringle)
> > 1] Has anyone seen any Virtual Memory programs for the Amiga?
> > 2] If so, has anyone used any of these Virtual Mem programs with Imagine?
>I use GigaMem. It works great. I tried it because the scene I'm rendering needs
>more than 20MB, and I removed my '040 board on which was 8MB. So I was left
>with 18MB instead of 26MB, and I had to use Gigamem. But for that reason, I
>cannot compare rendering times. But I don't think Virtual memory increases
I can confirm this also works well with smaller memory sizes.. I've rendered
12 meg scenes in 6 megs ram with no problem. Doesn't really seem to increase
render time too much, and hard drive use is minimal (some programs cause gigamem to swap pages to disk constantly). However, the more virtual memory you
use, the slower it gets. Virtual memory is great to have when rendering
(3d studio for the IBM has virtual memory built in..)
> BTW, Gigamem is a commercial package, it's not PD.
There is a PD virtual memory program, but it's much slower.
Remember you need a true '030 CPU with an MMU to use these..